@OdinakaDico : Thanks for the contribution and for providing the setup evidence references. After reviewing the content, we have some concerns that make us hesitant to merge this as-is.

The suggested causes don't match the symptom

Base URL misconfiguration and Pretty URL setup issues are unlikely to produce 404s specifically for CSS/JavaScript/asset files. Those problems typically manifest as page-level routing failures, not missing static files, because HumHub's published assets under /assets/ are served directly by the web server and don't pass through PHP routing at all. Pointing readers toward Pretty URL setup when they're seeing asset 404s risks sending them down the wrong path.

The steps confirm problems rather than fix them

The "Check the following points" list tells users what to verify but doesn't tell them what to do about it. Troubleshooting documentation is most useful when it closes the loop: symptom → likely cause → concrete resolution.

Asset 404s are not a common support issue for us

To be honest, we rarely receive support requests specifically about 404 errors on CSS/JS assets. This makes us wonder whether this entry is addressing a fairly isolated setup situation rather than a broadly recurring problem. The referenced evidence (S2-I04, S3-I02) isn't publicly accessible to us, so we can't assess how representative those cases are.

If this was triggered by a specific environment (e.g. a non-standard XAMPP or Windows setup, a subdirectory installation with a misconfigured web root), it might be worth narrowing the entry to that specific scenario with a concrete fix, rather than a general checklist.

We're happy to revisit if you can provide more context on the root cause and the fix that actually resolved it.

Sorry for the delayed response, I wanted to re-check the original setup evidence before replying.

I re-checked the evidence for S2-I04 and the related S3-I02 reference, and I agree that the PR as written was too broad. The evidence does not prove that Base URL or Pretty URL caused the asset 404s, so I agree that pointing users in that direction would be misleading.

The issue appears to have come from a Windows/XAMPP/Apache local setup with an installation path or document-root mismatch. The console showed missing frontend assets such as:

humhub-app.js:1 Failed to load resource: the server responded with a status of 404 (Not Found)
humhub-app.css:1 Failed to load resource: the server responded with a status of 404 (Not Found)
humhub-bundle.js:1 Failed to load resource: the server responded with a status of 404 (Not Found)

Later evidence also showed:

AH00112: Warning: DocumentRoot [C:/xampp/htdocs/humhub/web] does not exist

I also re-checked S3-I02, but it appears to point to the same underlying setup context rather than a separate confirmed case.

So I agree this should not be presented as a general asset-404 troubleshooting entry or linked to Pretty URL/Base URL setup. I’m happy to withdraw this PR as written. If a narrower Windows/XAMPP note would still be useful, I can prepare that separately with the exact scope and fix.

Thanks again for taking the time to explain the concern clearly.